home *** CD-ROM | disk | FTP | other *** search
/ SGI Performance Co-Pilot 1.3 / SGI Performance Co-Pilot 1.3.iso / dist / dist6.4 / pcp.idb / usr / share / catman / u_man / cat3 / PMAPI / pmfetcharchive.z / pmfetcharchive
Text File  |  1997-04-03  |  4KB  |  67 lines
  1.  
  2.  
  3.  
  4. PPPPMMMMFFFFEEEETTTTCCCCHHHHAAAARRRRCCCCHHHHIIIIVVVVEEEE((((3333))))                                            PPPPMMMMFFFFEEEETTTTCCCCHHHHAAAARRRRCCCCHHHHIIIIVVVVEEEE((((3333))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee - get performance metrics directly from an archive log
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<ppppccccpppp////ppppmmmmaaaappppiiii....hhhh>>>>
  13.  
  14.      iiiinnnntttt ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee((((ppppmmmmRRRReeeessssuuuulllltttt ********rrrreeeessssuuuulllltttt))))
  15.  
  16.      cccccccc ............ ----llllppppccccpppp
  17.  
  18. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  19.      ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee is a variant of ppppmmmmFFFFeeeettttcccchhhh(3) that may only be used when the
  20.      current Performance Metrics Application Programming Interface (PMAPI)
  21.      context is associated with an archive log.
  22.  
  23.      The _r_e_s_u_l_t is instantiated with all of the metrics (and instances) from
  24.      the next archive record, consequently there is no notion of a list of
  25.      desired metrics, and the instance profile of the PMAPI context is
  26.      ignored.
  27.  
  28.      It is expected that ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee would be used to create utilities that
  29.      scan archive logs, while the more common access to the archives would be
  30.      via the ppppmmmmFFFFeeeettttcccchhhh(3) interface.
  31.  
  32.      To skip records within the archive log, use ppppmmmmSSSSeeeettttMMMMooooddddeeee(3) to change the
  33.      collection time within the current PMAPI context, then call
  34.      ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee....
  35.  
  36.      Note that the _r_e_s_u_l_t returned by ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee is dynamically allocated,
  37.      and must be released using ppppmmmmFFFFrrrreeeeeeeeRRRReeeessssuuuulllltttt(3), not ffffrrrreeeeeeee(3C).  See ppppmmmmFFFFeeeettttcccchhhh(3)
  38.      and ppppmmmmFFFFrrrreeeeeeeeRRRReeeessssuuuulllltttt(3) for further details.
  39.  
  40.      ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee returns zero on success.
  41.  
  42. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  43.      PPPPMMMMAAAAPPPPIIII(3), ppppmmmmFFFFeeeettttcccchhhh(3), ppppmmmmFFFFrrrreeeeeeeeRRRReeeessssuuuulllltttt(3), ppppmmmmNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt(3), ppppmmmmSSSSeeeettttMMMMooooddddeeee(3) and
  44.      ppppmmmmTTTTrrrriiiimmmmNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3).
  45.  
  46. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  47.      PPPPMMMM____EEEERRRRRRRR____NNNNOOOOTTTTAAAARRRRCCCCHHHHIIIIVVVVEEEE
  48.           the current PMAPI context is not associated with an archive log
  49.  
  50.  
  51.  
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.